Managing Service Containers

This topic gives an overview about Service Containers.

A Service Container refers to an instance of a Java Virtual Machine (JVM) with Application Connectors and Connection Points attached to it. Several Service Containers can run within a single JVM. A Service Container in turn loads the Application Connectors and opens the Connection Points to read from.

A Service Container processes the request or response SOAP messages according to the formal set of conventions defined by SOAP. It is responsible for enforcing the rules that govern the exchange of SOAP messages and accesses the Service Containers provided by the underlying protocols through SOAP bindings.

Users with SystemAdmin role can monitor, stop, and start the Service Containers in their respective organizations. A Service Container can be started in the following ways:

• Automatic: The Service Container starts automatically after the OpenText Process Suite Platform (<instance name>) Service Container has started.
  
• Manual: You have to start the Service Container manually in the System Resource Manager application.
  
  Multiple Service Containers can run on a single machine.
  
  
• Creating a Service Container
  
• Modifying a Service Container
  
• Configuring OS Processes for a Service Container
  
• Monitoring Service Containers
  
• Viewing Memory Status Details
  
  By default, System Resource Manager displays the available Service Containers in a grid view. Click on the toolbar of the Service Containers App Palette to change the mode in which the Service Containers are displayed.
  
  Note: On a VMware or the low processing speed machines, CoBOC, Business Process Management, and Rule Management Service Containers might consume high CPU capacity during their startup. In such a case, set the com.cordys.cluster.timers.factor property to 2 in the wcp.properties to reduce the CPU utilization.